Skip to content

Change repository link to claude-memory-extractor - #2

Open
ramnathbabu wants to merge 1 commit into
obra:mainfrom
ramnathbabu:readme-patch-1
Open

Change repository link to claude-memory-extractor#2
ramnathbabu wants to merge 1 commit into
obra:mainfrom
ramnathbabu:readme-patch-1

Conversation

@ramnathbabu

@ramnathbabu ramnathbabu commented Nov 20, 2025

Copy link
Copy Markdown

Updated repository links for local installation instructions.

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Summary by CodeRabbit

  • Documentation
    • Updated installation and local development setup instructions with revised repository references and new build configuration steps.

✏️ Tip: You can customize this high-level summary in your review settings.

Updated repository links for local installation instructions.
@coderabbitai

coderabbitai Bot commented Nov 20, 2025

Copy link
Copy Markdown

Walkthrough

Documentation update that changes repository clone URLs from claude-memory to claude-memory-extractor and adds npm build and link steps to both global installation and local development instructions. No functional code changes.

Changes

Cohort / File(s) Summary
Documentation Setup Instructions
README.md
Updated repository references from claude-memory to claude-memory-extractor; added npm install, npm run build, and npm link commands to installation and local development sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Verify repository URL changes are correct and intentional
  • Confirm added build steps (npm install && npm run build) and npm link are appropriate for the new repository structure

Poem

🐰 A hop, a skip, from old to new,
The docs now point to paths more true,
With npm steps to build and bind,
The clearest instructions we shall find! 📚✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and clearly describes the main change: updating repository links to point to claude-memory-extractor instead of the previous repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 384e030 and e82c2e0.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🔇 Additional comments (1)
README.md (1)

67-73: Verify consistency with Option 1 installation approach.

Option 2 correctly omits npm link since it runs the CLI directly from the built distribution, which is appropriate for local development. Confirm this distinction is intentional and that users running the direct command (./dist/cli.js extract) will work as expected without global installation.

Comment thread README.md
Comment on lines +58 to 62
git clone https://github.com/obra/claude-memory-extractor.git
cd claude-memory-extractor
npm install && npm run build
npm link
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

Verify the repository URL is correct and reachable.

The clone URL has been updated from claude-memory to claude-memory-extractor. Confirm that this repository exists, is accessible, and reflects the current source of truth for this project.


🏁 Script executed:

#!/bin/bash
# Verify the new repository URL is accessible and contains the expected code
git ls-remote https://github.com/obra/claude-memory-extractor.git HEAD > /dev/null 2>&1
if [ $? -eq 0 ]; then
  echo "✓ Repository is accessible"
  git ls-remote https://github.com/obra/claude-memory-extractor.git | head -5
else
  echo "✗ Repository URL is not reachable"
fi

Length of output: 246


Repository URL verification passed. Now checking for any other references to the old repository name in the codebase.


---

🏁 Script executed:

```shell
#!/bin/bash
# Search for remaining references to "claude-memory" (without -extractor suffix)
# in the codebase to ensure consistency
rg -n "claude-memory(?!-extractor)" --type md --type json --type yaml --type txt --type js --type ts 2>/dev/null || echo "No matches or search completed"

Length of output: 30


🏁 Script executed:

#!/bin/bash
# Also check for any repository references that might be in package.json or similar config files
fd -e "package.json" -e "package-lock.json" -e ".github" -type f | head -20

Length of output: 170


🏁 Script executed:

#!/bin/bash
# Get a count of all "claude-memory" occurrences to understand scope
rg -c "claude-memory" 2>/dev/null | grep -v ":0$" || echo "Search completed"

Length of output: 69


Found lingering references to "claude-memory" across multiple files. Examining the actual content to determine if these are incomplete updates or intentional references.


---

🏁 Script executed:

```shell
#!/bin/bash
# Show context for "claude-memory" references in README.md
rg -n -B2 -A2 "claude-memory" README.md

Length of output: 1014


🏁 Script executed:

#!/bin/bash
# Check src/cli.ts references
rg -n -B2 -A2 "claude-memory" src/cli.ts

Length of output: 533


🏁 Script executed:

#!/bin/bash
# Check package.json
rg -n "claude-memory" package.json

Length of output: 123


🏁 Script executed:

#!/bin/bash
# Check docs/guides/quick-start.md
rg -n -B2 -A2 "claude-memory" docs/guides/quick-start.md

Length of output: 535


Update inconsistencies: repository name changes not applied uniformly across the codebase.

The README.md lines 58-62 are correctly updated to use the new claude-memory-extractor repository URL. However, the broader repository rename is incomplete:

  • package.json line 31: Repository URL still references https://github.com/obra/claude-memory.git
  • package.json line 2: Package name still "claude-memory" (should align with repository name)
  • src/cli.ts line 74: Help text URL still points to https://github.com/obra/claude-memory
  • docs/guides/quick-start.md lines 18-19: Clone instructions still reference old repository and directory name

These should be updated to maintain consistency with the new repository name across all user-facing and configuration references.

🤖 Prompt for AI Agents
In README.md lines 58-62 and across the repo (package.json lines 31 and 2,
src/cli.ts line 74, docs/guides/quick-start.md lines 18-19) the project was
partially renamed to claude-memory-extractor but several user-facing and config
references remain as claude-memory or the old GitHub URL; update package.json
name (line 2) to "claude-memory-extractor", update the repository URL (line 31)
to https://github.com/obra/claude-memory-extractor.git, change the help text URL
in src/cli.ts (line 74) to the new repo URL, and update the clone/path
instructions in docs/guides/quick-start.md (lines 18-19) to use the new
repository and directory name so all references are consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant